The system will at certain times autologout an idle job after giving
it a five minute warning.  Sometimes the system will detach an idle
job instead of logging it out.

In prime time (10am to 6pm weekdays), a job is subject to autologout after
not running for 10 minutes.  In non-prime time, the minimum idle time
before autologout is 20 minutes.  The warning will come 5 minutes before
potential autologout (e.g., 5 minutes after not running in prime time).

An idle job will be considered for autologout when either
	(1) the system has five or fewer vacant job slots, or
	(2) the job is on a Data Disc terminal and there are three or
	    fewer free DD channels, or
	(3) the job is on a high-speed dialup line and there are
	    two or fewer such lines free, or
	(4) the job has been idle for over 2 hours, even if there
	    is no resource scarcity.
Also, during the five minutes between the warning and the logout (or
detach if the problem is a lack of DD channels or dialup lines), a check
is made each minute, and the resource scarcity must continue throughout
the five minutes, or else the job will no longer be deemed warned of an
autologout.  In other words, the scarcity must last five consecutive
minutes for you to be logged out or detached.

Here are two ways in which the user can affect how autologout works
on his jobs.

1.  The LIV privilege, available to anyone, means "never log this job out"
    and has no other effects (e.g., the job may still be detached).  This
    privilege may be enabled by command (ENABLE LIV) or by UUO, but it
    goes away whenever a new program is run by monitor command.  It is
    meant to be used, for example, when you are debugging--but not
    running--a dead core image.

2.  The DET privilege, available to anyone, may be enabled by command
    (ENABLE DET) or UUO and is not reset unless you explicitly disable it.
    It means "I would rather be detached than logged out".  If you do NOT
    enable this privilege, your job will be logged out, not detached, even
    if the problem is one of DD channels or dialup lines rather than job
    slots.  The motivation for this change is that if you enable this
    privilege you presumably know that you may be producing detached jobs.
    Note that DET does not prevent the job from being logged out if there
    is a job slot shortage.  The DETACH option for the LOGIN line in
    OPTION.TXT will enable the DET privilege automatically upon normal
    login.

Jobs which are eligible for autologout (or detach) are divided into two
categories.  You are in category B if you have a DSK (or new UDP) file
open for output, or if you have a device other than DSK or TTY open for
anything.  Otherwise you are in category A.  Whenever the spy needs to log
out (or detach) anyone, it first does its thing to all jobs in category A.
It updates its count of free jobs, channels, and dialup lines assuming
that the jobs logged out will really release their resources.  (In other
words, it does not wait the 15 seconds that it takes for a DD channel to
be freed up, etc.)  On that assumption, if there is still a scarcity,
category B jobs will be logged out or detached if they have the scarce
resources.